Systems and methods for facilitating open source intelligence gathering

ABSTRACT

Systems and methods (e.g., utilities) for use in providing automated, lightweight collection of online, open source data which may be content-based to reduce website source bias. In one aspect, a utility is disclosed for use in extracting content of interest from at least one website or other online data source (e.g., where the extracted content can be used in a subsequent search query). In other aspects, utilities are disclosed that are operable to perform various types of analyses on such extracted content and present graphical representations of such analyses on a display of a client device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Divisional application of and claims priority to: U.S. patent application Ser. No. 14/091,024, entitled “SYSTEMS AND METHODS FOR FACILITATING OPEN SOURCE INTELLIGENCE GATHERING” and filed on Nov. 26, 2013; U.S. patent application Ser. No. 13/045,128, entitled “SYSTEMS AND METHODS FOR FACILITATING OPEN SOURCE INTELLIGENCE GATHERING” and filed on Mar. 10, 2011; and U.S. Provisional Patent Application No. 61/312,341, entitled “WISDOM SYSTEMS AND METHODS” and filed on Mar. 10, 2010. The entirety of each of these applications is incorporated herein by reference.

FIELD OF THE INVENTION

The present invention relates generally to open source intelligence gathering, and more particularly to the automated collection and subsequent processing of open source data to extract meaningful information.

BACKGROUND OF THE INVENTION

Open source intelligence (OSINT) is a form of intelligence collection management that involves finding, selecting, and acquiring information from publicly available sources and analyzing it to produce actionable intelligence. In the intelligence community (IC), the term “open” refers to overt, publicly available sources (as opposed to covert or classified sources); it is not necessarily related to open-source software or public intelligence.

For example, American military professionals have collected, translated, and studied articles, books, and periodicals to gain knowledge and understanding of foreign lands and armies for over 200 years. The recent exponential growth in computer technology and the Internet has placed more public information and processing power at the finger tips of military personnel and other users than at any time in the past. Internet sites (i.e., websites) enable users to participate in a publicly accessible communications network that connects computers, computer networks, and organizational computer facilities around the world. Through use of the Internet, users can locate, monitor and observe various websites to obtain any quantity of useful information (e.g., in the case of the military, enemy intentions, capabilities, activities, etc.). To name only a few, websites of news outlets, television stations, forums, and the like may be monitored and/or searched for particular terms or topics of interest during such OSINT gathering.

SUMMARY OF THE INVENTION

The speed of Internet activity has exceeded the pace of OSINT collection and analysis. As a result, open source intelligence gatherers have been presented with the basic trade-off of analysis quality versus production timeliness. Some existing systems merely collect an abundance of information and then leave it to the service subscribers to determine that which is of value. For instance, existing systems allow users to perform queries on one or more data sources and then return what may be thousands of results to the user based on the query parameters. However, many if not most of the results may be uninteresting to the user due to sub-optimal search engine technologies and automated collection processes.

Furthermore, much of the content making up a website or other data source and on which a query or analysis may be performed may be of a form that is not important to a user and/or which may skew search results and subsequent analyses. For instance, a particular page on nytimes.com including an article discussing the results of a recent major sporting event may also include a small advertisement directed to no fee checking with a major bank. As part of the same example, imagine a user interested in learning about any recent developments in relation to the loan fees charged by the World Bank to third world countries performs a search using any appropriate search tools utilizing the query parameters “world,” “bank,” “fees” and “loans.” As the New York Times article about the sporting event happens to include an advertisement directed to “no fee checking” with a “major bank,” the sporting article may be presented as one of the results to the user's search query, much to the user's dismay.

It has been determined that systems, apparatuses and methods (i.e., utilities) are needed that can both provide for automated, lightweight collection of online, open source data which may be content-based to reduce website source bias. In one aspect, a utility is disclosed for use in extracting content of interest from at least one website or other online data source (e.g., where the extracted content can be used in a subsequent query and/or analysis). Depending upon the particular objects or goals of a subsequent query or analysis, “interesting” content may be the actual text of a webpage (e.g., just the text of an article on the webpage, and not any text or other characters associated with advertisements or navigation sections). In another scenario, the interesting content may just be any HTML links (e.g., “inlinks”) contained within the article on the webpage. For instance, a user may be interested in news articles or blog postings that have inlinks to a particular URL. For purposes of this discussion, the terms “query,” “search,” “filter” and the like (along with their respective variations) will be used interchangeably.

The utility may include obtaining source code used to generate the at least one website on a display, where the source code includes a plurality of elements and each element includes at least one tag comprising at least one tag type; parsing the source code using a processor to obtain a node tree including a plurality of nodes arranged in a hierarchical structure, where each node comprises one of the elements, and wherein one of the plurality of nodes comprises a root node; determining a tag type of a node under the root node; assigning a heuristic score to the node based at least in part on the tag type of the node; repeating the determining and assigning for one or more additional nodes of the node tree; and generating, using the processor, an object that includes content associated with nodes of the node tree having heuristic scores indicating that such content is of interest.

This utility allows any desired content to be extracted from a piece of data (e.g., the source code of a webpage) with little or no prior knowledge of the page and with little or no human interaction. For instance, any appropriate server and/or process may collect large volumes of website data on a scheduled basis, utilize this utility to extract interesting content, and then index such content in a data store for subsequent searching and/or analysis. Furthermore, the various details of the originally observable webpage (e.g., graphics, advertisements, etc.) may also be available to a user (e.g., by storing such original data in the data store).

In addition to the aforementioned utilities that allow for automated and lightweight collection of online, open source data, it has also been determined that various utilities that provide analytic visualizations of such collected open source data are needed to, for instance, allow for trending and discovery of interesting and/or important developments and occurrences. For example, the various utilities disclosed herein can act as early warning systems for emerging sentiments and ideologies that are adverse to U.S. interests. In this regard, and in another aspect, a utility is disclosed that allows for the determination (e.g., automated determination) of a sentiment of a term among a plurality of data sets. For instance, a user may initially define a “scenario” made up of one or more keywords and operators (collectively, “scenario parameters”) that focus on attacks performed by Al Qaeda. The scenario may then be used to perform a query of online, open source data in any appropriate manner to obtain a number of search results (e.g., a list of relevant websites). In addition to the search results, the user may be benefited by visually observing a sentiment (e.g., positive, negative, neutral) of one or more terms (e.g., Osama Bin Laden) of the scenario parameters and/or terms that are frequently used throughout the returned results over one or more time periods.

In this regard, the utility includes receiving the x most frequently disclosed terms (e.g., top five, top ten) among a plurality of data sets (e.g., plurality of objects including content extracted from websites using the above-discussed utility) during a time period (e.g., day, week), where x is a positive integer; for each of the x most frequently disclosed terms during the time period: determining, using a processing engine, a volume of the plurality of data sites disclosing the term; and obtaining, using the processing engine, a sentiment of the term among the plurality of data sites; and presenting, on a display, a first graphical representation illustrating the sentiment and volume of each of the x most frequently disclosed terms during the time period.

That is, as opposed to a user manually selecting those words or terms for which to determine a sentiment, the disclosed utility may automatically select (e.g., based on frequency of use in the returned search results or in other appropriate manners) which terms to perform a sentiment analysis on, and then may present the results of such sentiment analysis on a display (e.g., in the form of sparkcharts or other graphical representations that display the sentiment over a selected time period). Advantageously, a user need not manually review the search results for terms on which to perform sentiment and volume analyses. Furthermore, a user may be more interested in reviewing sentiment/volume analyses for terms that are more frequently disclosed (i.e., other than terms like “a,” “or,” etc.) than other terms as the mere fact that the term is frequently disclosed may indicate a greater relative importance of the term in relation to other terms.

Furthermore, the posts or websites that contain the particular terms that are automatically selected by the utility may be the posts for which sentiment is determined. Stated otherwise, the text of those websites (i.e., their extracted content) where the particular terms are found may be the text that is used to determine if the overall sentiment of the term is positive, negative or neutral. For example, if a website where one of the particular terms (e.g., Mubarak) for which a sentiment analysis is being performed contains 30 instances of “hate” but only 5 instance of “like,” then the website may be labeled as a “negative” website/data site. A similar procedure may be performed on other websites of the search query results for the term Mubarak. Subsequently, an overall sentiment for the term Mubarak for a particular time period or time increment may be obtained by subtracting the number of “negative” sites where the term Mubarak is found from the number of “positive” sites where the term Mubarak is found to obtain a result, and then using the result to determine whether the term Mubarak should be indicated as having a positive, negative or neutral sentiment for the time increment/period. Other appropriate types of statistical analysis may be performed to obtain term sentiments as well.

In addition to the sentiment, the utility may also automatically determine a volume of use of such terms and additionally present graphical representations of such volumes on the display (e.g., alongside and/or integrated with the determined sentiments). Furthermore, the utility may allow for the manual and/or automatic selection of what will be referred to as “stop words,” that is, words or terms that would not be used as part of the sentiment/volume analysis, even if such words were, for instance, one of the most frequently used words in the search query results (e.g., “a,” “the,” etc.).

In another aspect, a utility for creating a hierarchical signature for a website or other online data source is disclosed that can allow a user to, for instance, discern the ebb and flow of topics over any appropriate time period on individual websites as well as on automatically clustered sites (e.g., using any appropriate clustering methods or processes) that have similar signatures. More specifically, a “signature” of a website or other online data source may be obtained by determining a frequency or prevalence of particular terms on one or more pages of the website over a time period, and then appropriately presenting such signature on a display for visualization by a user. For instance, a frequency of each of the terms “counterterror,” “government,” “military,” and “president” on each of a number of websites (e.g., those websites returned corresponding to a particular scenario) may be determined, the results may be normalized to “high,” “medium” and “low,” and then such normalized results may be presented for a user on a display in the form of a color coded chart (e.g., where darker colors represent higher frequency and lighter colors represent lower frequency). This utility may allow such signatures to be leveraged to track discussions, infer textual linkages among websites, discover communities of interest according to topic saliency, and the like.

This utility involves identifying at least one textual hierarchy including at least first and second levels, where the first level comprises at least one textual category and the second level comprises at least one term that describes the at least one textual category; determining a number of occurrences of the at least one term from a number of pages of at least one website during a time period; first obtaining, using a processing engine, a hierarchical signature of the at least one term that represents a prevalence of the at least one term on the at least one website; second obtaining, from the first obtaining step, a hierarchical signature of the at least one textual category that represents a prevalence of the at least one textual category on the at least one website; establishing a hierarchical signature of the at least one website utilizing the hierarchical signature of one or more of the at least one term and the at least one textual category; and presenting, on a display, a graphical representation of the hierarchical signature of the at least one website, where the graphical representation illustrates the prevalence of one or more of the at least one term and the at least one textual category.

Of note, this utility not only obtains a hierarchical signature of one or more terms for one or more websites (by determining a prevalence of such terms on such websites), but also obtains a “first level” signature of a category that represents or encompasses the one or more terms by, for instance, averaging (and/or performing other appropriate types of statistical analyses) the “second level” hierarchical signature(s) of the one or more terms. For instance, a “communications” category could be manually and/or automatically made up of the terms “audio,” “propaganda,” “statement,” and “video”. Numerous other categories could be manually and/or automatically determined (e.g., “government,” “Congress”). In this regard, a “first level” hierarchical signature of a website may be made up of the particular frequencies of a number of categories and may be presented on a display in the form of, for instance, a number of adjacent graphical icons, where a color of each graphical icon represents the prevalence of one of the categories on the website. Furthermore, a “second level” hierarchical signature of a website may be made up of the particular frequencies of the terms making up one or more of the aforementioned categories on the website (e.g., in the case of the category “communications,” the terms “audio,” “propaganda,” “statement,” and “video”).

The at least one textual hierarchy in this utility which forms the basis of the hierarchical signature determination may be identified in any appropriate way (e.g., manually, automatically). In one arrangement, scenario parameters used to perform a query that turned up the at least one website for which the hierarchical signature is being determined may be at least partially used in the textual hierarchy (e.g., as first-level categories and/or second-level terms). In another arrangement, a number of default categories with respective terms may be defined and which may be manually selected by a user as part of an analysis of search results. In a further arrangement, one or more “community” of “network” signatures may be determined. For instance, any appropriate standard tools or algorithms may be used to determine one or more communities of interest from the results of an open source search query (e.g., each community including a plurality of websites or online data sources having one or more common traits or characteristics, such as a number of websites taking a particular view of an important world event). The disclosed utility may then “roll up” or otherwise combine the “site signatures” (e.g, made up of first and/or second level signatures) of each of the websites to obtain a “community signature”.

In another aspect, a utility is disclosed for use in inferring an information flow network that can allow information flows between and among websites and authors to be determined over time. The utility can capture relationships between people and entities in online discussion environments (e.g., forums, blogs) and enable a network of relationships between entities that are discussing topics of interest to be discovered and “verified” automatically. For instance, the utility can build connections by way of analyzing metrics such as frequency of posts or postings (e.g., blog entries), frequency of responses, context of posts, and the like to enhance identification of significant relationships.

The utility includes receiving information related to a plurality of portions of source code used to generate a plurality of online data sources (e.g., blog postings, news articles, web pages, etc), where the information allows a uniform resource locator (URL) to be obtained for at least one of the data sources; determining, from the information using a processor, whether any of the plurality of online data sources refers to another online data source during a first of a plurality of time periods (e.g., days), where any online data source that refers to another online data source comprises a “secondary data source”, and where any online data source that is referred to by another online data source comprises a “primary data source”; in response to at least some of the plurality of online data sources referring to other online data sources, obtaining, from the information, a unique URL for each of the primary and secondary data sources; repeating the determining and obtaining for additional time periods; and presenting, on a display, a graphical representation of an information flow network that illustrates one or more information flow links connecting and representing information flows from primary data sources to secondary data sources over the plurality of time periods.

For instance, in the context of a news article on nytimes.com discussing President Obama's new education agenda that includes an HTML link to whitehouse.gov in the body of the article, the graphical representation may include a graphical icon representing the primary data source URL “whitehouse.gov,” another graphical icon representing the secondary data source URL “nytimes.com,” and another graphical icon (e.g., an arrow) representing an information flow from the whitehouse.gov icon to the nytime.com icon. In other words, the information flow may be determined by “reversing the inlinks” disposed within a particular online data source. In one arrangement, the source code corresponding to the primary and secondary data source URLs may have been previously harvested utilizing any appropriate search engine(s) and/or process(es) and stored in one or more data stores for retrieval by the utility.

In one arrangement, unique URLs may be constructed for online data sources. For instance, as each posting on a blog site has the same URL or IP address (i.e., the URL or IP address of the blog site), it may otherwise be difficult to establish online information flow networks and thereby map information flows among a number of postings. In this regard, one embodiment involves constructing a unique URL for each posting of a blog site (or other online data source) by utilizing the URL of the blog site or website along with one or more identifiers of or associated with the individual posting as inputs to any appropriate algorithm or logic operable to generate or create a unique URL for the particular posting.

In another arrangement, the utility may further include, in response to a user manipulable device or component (e.g., cursor, user's finger) being positioned over a primary data source graphical icon (e.g., the whitehouse.gov icon discussed above), modifying a feature of the primary data source graphical icon (e.g., to assume a first color), modifying a feature of any secondary data source graphical icons of the primary data source graphical icon (e.g., modifying the nytimes.com icon discussed above to a second color), and modifying a feature of the information flow link graphical icons connecting the primary data source graphical icons and the secondary data source graphical icons (e.g., to a third color). For instance, the three colors may be different from the colors of other graphical icons in the graphical representation of the online information flow network to allow a user visually observe the particular manner in which a particular post/blog entry affects or is affected by information flows in the network.

The various aspects discussed herein may be implemented via any appropriate number and/or type of platforms, modules, processors, memory, etc., each of which may be embodied in hardware, software, firmware, middleware, and the like. Various refinements may exist of the features noted in relation to the various aspects. Further features may also be incorporated in the various aspects. These refinements and additional features may exist individually or in any combination, and various features of the aspects may be combined. In addition to the exemplary aspects and embodiments described above, further aspects and embodiments will become apparent by reference to the drawings and by study of the following descriptions.

DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and further advantages thereof, reference is now made to the following Detailed Description, taken in conjunction with the drawings, in which:

FIG. 1 illustrates a functional block diagram of a system that may be used to perform open source intelligence gathering and related analytical visualizations.

FIG. 2 illustrates a functional block diagram of a backend processing engine of the system of FIG. 1.

FIG. 3 illustrates a functional block diagram of a client device of the system of FIG. 1, and showing a dashboard that may be run on or accessible by the client device to allow a user to administer scenarios for online searches, observe search results, perform one or more analyses on such results, and the like.

FIG. 4 illustrates a screenshot of a dashboard that may be used to expose and manipulate the various utilities disclosed herein.

FIG. 5 illustrates another screenshot of the dashboard of FIG. 4.

FIG. 6 illustrates another screenshot of the dashboard of FIG. 4.

FIG. 7 illustrates another screenshot of the dashboard of FIG. 4.

FIG. 8 illustrates another screenshot of the dashboard of FIG. 4.

FIG. 9 illustrates a functional block diagram of a content extraction module of a collection manager of the backend processing engine of FIG. 2 that may be used to extract meaningful content from webpages or other online data sources.

FIG. 10 illustrates a representative segment of HTML code including a number of elements on which the content extraction utility disclosed herein may be practiced.

FIG. 11 illustrates a hierarchical parse tree including a number of nodes representing the elements of FIG. 10.

FIG. 12 illustrates a protocol or flow diagram for extracting one or more types of content from a webpage or other type of online content.

FIG. 13 illustrates an object including content extracted from an online data source using the content extraction module of FIG. 9.

FIG. 14 illustrates another screenshot of the dashboard of FIG. 4.

FIG. 15 illustrates a functional block diagram of a toolbox of the backend processing engine of FIG. 2, where the toolbox include a number of tools that may be used to analyze information obtained from one or more search services.

FIG. 16 illustrates a functional block diagram of a sentiment analysis engine of the toolbox of FIG. 15.

FIG. 17 illustrates a protocol or flow diagram for determining and presenting on a display a graphical illustration of a sentiment and volume of one or more terms of a website or other online data source over one or more time periods.

FIG. 18 illustrates another screenshot of the dashboard of FIG. 4.

FIG. 19 illustrates a functional block diagram of a hierarchical signature engine of the toolbox of FIG. 15.

FIG. 20 illustrates a protocol or flow diagram for establishing a hierarchical signature for a website or online data source over one or more time periods and then presenting a graphical representation of the hierarchical signature on a display.

FIG. 21 illustrates another screenshot of the dashboard of FIG. 4.

FIG. 22 illustrates another screenshot of the dashboard of FIG. 4.

FIG. 23 illustrates another screenshot of the dashboard of FIG. 4.

FIG. 24 illustrates a protocol or flow diagram for inferring or extracting an online information flow network from a plurality of online data sources and then presenting a graphical illustration of the network on a display that illustrates information flows between a number of posts and/or authors.

FIG. 25 illustrates another screenshot of the dashboard of FIG. 4.

FIG. 26 illustrates another screenshot of the dashboard of FIG. 4.

FIG. 27 illustrates another screenshot of the dashboard of FIG. 4.

FIG. 28 illustrates another screenshot of the dashboard of FIG. 4.

DETAILED DESCRIPTION

Reference will now be made to the accompanying drawings, which assist in illustrating the various pertinent features of the various novel aspects of the present disclosure. While the various disclosed utilities will be described primarily in relation to OSINT, these utilities may also be used in other environments where it would be useful to efficiently navigate through and/or harvest large volumes of information and/or data (e.g., data that is internal to an organization and not publically accessible) and perform numerous types of analytical visualizations on such harvested data. In this regard, the following description is presented for purposes of illustration and description. Furthermore, the description is not intended to limit the inventive aspects to the forms disclosed herein. Consequently, variations and modifications commensurate with the following teachings, and skill and knowledge of the relevant art, are within the scope of the present inventive aspects.

FIG. 1 illustrates a functional block diagram of a system 10 that may be used to perform data gathering (e.g., for open source intelligence) and related analytics and subsequently present such gathered data and analytics to one or more users via one or more client devices 22. At the heart of the system 10 may be what will be referred to as the “WISDOM” server 14 which, as will be appreciated with reference to the ensuing discussion, is generally operable to obtain open source intelligence information from one or more web resources or search services 18 (e.g., by querying a number of search services 18 according to any user-defined schedule, such as each morning) over at least one wired or wireless network 24 (e.g., Internet, WANs, LANs), store such information in at least one data store 46, perform one or more types of processing and analyses on such obtained information, and make such information and analyses available to users via client devices 22 over a network 25 (e.g., Internet, WANs, LANs) via a “dashboard” or other type of console or user interface running on and/or accessible by the one or more client devices 22. In contrast to previous OSINT systems, the present system 10 is lightweight for enhanced intelligence retrieval and may be “content-based” (i.e., focuses on the substantive content of a webpage, e.g., the text of the article, instead of extraneous portions of the webpage, e.g., advertisements, navigation sections, etc.). It should be appreciated that the terms “post,” “website,” “webpage,” “data site,” “online data source,” and the like will be used interchangeably herein, unless otherwise specified.

The WISDOM server 14 may include at least one memory module 26 (e.g., RAM or other volatile memory), at least one processing module or processor 30 for executing computer readable instructions from the memory module 26, at least one storage module 34 (e.g., hard disk or other non-volatile memory), at least one monitor or display 38, and/or other peripheral devices or components 42. The data store 46 may store retrieved open source information (e.g., original source code, objects 94, discussed below) in addition to the results of any analyses performed on the information according to any appropriate structured arrangement that allows for efficient input and retrieval of data (e.g., RDBMS). While the data store 46 is shown as being separate from the memory module 26 and storage module 34, the data store 46 may be at least partially implemented within one or more of the memory module 26, storage module 34, and the like. In any event, the various components may be logically connected by any appropriate bus (not shown).

Furthermore, although the WISDOM server 14 has been illustrated as being a single device (e.g., server, laptop, desktop, mobile device, and/or other computing device), one or more functionalities or processes of the WISDOM server 14 may be allocated among a number of machines or devices which may or may not be embodied in a single housing. For instance, it is contemplated that the data collection process that will be discussed could be handled by a first machine or group of machines or processes while the subsequent analyses performed on such collected open source data could be handled or performed by a second machine or group of machines or processes.

The WISDOM server 14 may include a backend processing engine 50 that generally coordinates the querying, retrieval and subsequent filtering and analyses of open source intelligence information to extract and present meaningful information to users. The WISDOM server 14 may also include a data access layer 54 that facilitates storage and retrieval of information and data in relation to the data store 46. As shown in FIG. 2, the backend processing engine 50 may include a query manager 56 for executing queries of search services 18 based on one or more “scenarios” defined by a user, a collection manager 58 for retrieving the source code and/or content of search results (e.g., posts) returned by the query manager 56, and a toolbox 62 for performing one or more analyses on the collected source code and/or content.

Before discussing the query manager 56, collection manager 58 and toolbox 60 of the backend processing engine 50 of the WISDOM server 14 in more detail, a brief discussion of a client device 22 will now be presented. Turning to FIG. 3, a representative client device 22 (for use with the system 10 of FIG. 1) may include at least one memory module 326 (e.g., RAM or other volatile memory), at least one processing module or processor 330 for executing computer readable instructions from the memory module 326, at least one storage module 334 (e.g., hard disk, flash memory card or stick, other non-volatile memory, etc.), at least one monitor or display 338, and/or other peripheral devices or components 342, all of which may be logically connected by a bus in a conventional manner.

Running on the client device 22 (and/or running on the WISDOM server 14 and accessible by the client device 22 by any appropriate web interface) may be a console or dashboard 346 (e.g., software application) that is broadly operable to allow a user to define one or more scenarios and/or sub-scenarios (each made up of one or more key words and/or operators) to be used by query manager 56 as part of a query of one or more search service 18, perform filtering (e.g., via key words and/or operators) according to the content of returned posts corresponding to one or more of the scenarios (i.e., define one or more “sub-scenarios”), manage and observe a number of visual analytics (e.g., term sentiments, website hierarchical signatures, etc.) related to search results, and the like. Stated otherwise, the dashboard 346 may allow a user to perform a more targeted and/or “on the fly” analysis of previously obtained and stored open source information. For instance, upon a user modifying and/or redefining scenarios, filter queries, and the like, the various visual analytics may be automatically re-determined or updated and then re-presented on the user's display.

As discussed previously, client device 22 may be in appropriate communication with WISDOM server 14 (e.g., via data access layer 54) over network(s) 25. Among other modules, managers and the like that will be discussed in more detail later in this discussion, the dashboard 346 may include a scenario generator 350 that accepts scenario parameters from a user (e.g., key words, Boolean operators) for defining one or more scenarios. The scenario generator 350 may then coordinate with the query manager 56 to execute periodic queries for open source information from one or more search services 18 via network(s) 24 based on such scenarios and their associated scenario parameters.

Turning to FIG. 4, a screenshot 400 (e.g., splash screen) of dashboard 346 is illustrated as may be presented to a user on a display (e.g., display 338 of client device 22) upon starting or running dashboard 346. The dashboard 346 may, for example, be displayed via a web browser application executing on the client device 22. The screenshot 400 may include an area 401 (e.g., a welcome box) that allows a user to choose whether to observe and/or analyze posts from scenarios 403 (e.g., “Libya_Instability,” “Saudi_Arabia_Instability,” “Yemen_Instability,” etc.) previously generated and run by the scenario generator 350 and/or to create or configure one or more new scenarios via the scenario generator 350 by manipulating (e.g., clicking, tapping) a button 405 (or other user manipulable feature). For a user's reference, the area 401 may include a current number of posts available (e.g., stored on data store 46 of WISDOM server 14) for each respective scenario 403.

FIG. 5 illustrates another screenshot 409 of the dashboard 346 upon a user choosing to create a new scenario by manipulating button 405. As shown, the area 401 may include one portion 411 that allows a user to choose one of a number of templates (e.g., “Generic Template,” “Regional Conflict,” “Organization,” etc.) with which to build or create a scenario and another portion 413 (e.g., “Advanced Mode”) that provides a user with more flexibility in customizing a scenario. Turning to FIG. 6, another screenshot 415 of the dashboard 346 may be presented on a display upon a user choosing to build a scenario from a template (e.g., the “Regional Conflict” template). Each template may include a number of pre-defined cells 417 (or other types of features such as drop down menus and the like) that allow for the entry and/or selection of a scenario name, a template name (e.g., for creating and saving a new template), and one or more keywords and/or phrases (e.g., parameters) according to keyword or phrase type or classification (e.g., location, conflict type, organization type, organization name, etc.) upon which a scenario query will be run by the query manager 56.

In one embodiment, the scenario generator 350 may automatically embed operators (e.g., and, or, not, etc.) among, within and/or between the various classifications as appropriate. In one arrangement, “and” operators may be automatically embedded between each of the classifications and “or” operators may be automatically embedded between each of the keywords/phrases within a particular classification before the collective scenario parameters are passed to the query manager 56. For instance, entering “Afghanistan” and “Yemen” in the “Location” cell 417 and “Hezbollah” and “al-Qa'ida” in the “Organization Name” cell 417 would result in the search string ((Afghanistan or Yemen) and (Hezbollah or al-Qa'ida)) being used by the query manager 56 for a query of search services 18 based on the particular scenario. Such search strings may be stored in data store 46 according to scenario name, user name, etc. Of course, numerous other types of templates are envisioned for use in configuring a scenario, where each may have one or more different types of cell classifications and/or embedded operators. For instance, and returning to the screenshot 409 of FIG. 5, a user's selection of a “Generic Template” in portion 411 may result in different classification cells 417 and/or embedded operators in the screenshot 415 of FIG. 6.

FIG. 7 illustrates another screenshot 419 that may be presented on a user's display for use in building a scenario upon the user choosing to enter the “Advanced Mode” in portion 413 of FIG. 5. Similar to the screenshot 415 of FIG. 6, this screenshot 419 may include a number of pre-defined cells 421 (or other types of features such as drop down menus and the like) that allow for the entry and/or selection of a scenario and one or more keywords and/or phrases (e.g., parameters) according to keyword or phrase type or classification (e.g., messenger, modifier, messages, etc.) upon which a scenario query will be run by the query manager 56. However, this screenshot 419 allows a user to manually embed operators within each of the cells 421 as appropriate. In any event, a user may choose to save a created scenario (e.g., by manipulating the “save” button shown in FIG. 7 which may also be presented to a user in the screenshot 415 of FIG. 6) which may then be used by the query manager 56 in performing periodic queries (e.g., each morning, twice a day, etc.) of one or more search services 18 for posts matching the scenario parameters.

Once a scenario has been created, a user may edit the scenario as necessary. For instance, FIG. 8 illustrates another screenshot 423 of the dashboard 346 that may be presented to the user (e.g., upon manipulating a “Scenario Editor” button 410). This screenshot 423 may include a number of pre-defined cells 425 (or other types of features such as drop down menus and the like) which may be similar to those used to initially create the scenario and that allow for the entry and/or selection of the scenario name (e.g., to edit a previously chosen scenario name), a template name (e.g., to allow a particular scenario to be saved as a template for future use in generation of a scenario), and one or more keywords and/or phrases (e.g., parameters) according to keyword/phrase type or classification (e.g., “Primary Subject,” “Secondary Subject,” “Other,” etc.) upon which a scenario query will be run by the query manager 56. This screenshot 423 may also include a number of buttons 427 (or other user manipulable features) that allow a user to selectively run, delete and/or save a scenario and/or exit the scenario editing feature.

Although not shown, other types of scenario parameters are envisioned such as time periods or date ranges, particular search services to be used, and the like. Furthermore, while the dashboard 346 has been described as presenting the splash screen of FIG. 4 to a user upon starting or running the dashboard 346, it is envisioned that other screenshots (e.g., those discussed elsewhere herein) could be initially presented to a user upon starting the dashboard 346.

Returning to FIGS. 1-2, each of the search services 18 may be, for instance, a different web feed aggregator (e.g., Google® News) that is operable to subscribe to a number of “web feeds” (i.e., frequently updated content such as RSS feeds) from a number of news or data outlets (e.g., MSNBC, Washington Post, Al Jazeera) and/or other online data sources. In this regard, the query manager 56 may pass parameters obtained from data store 46 for a particular scenario to the one or more search services 18 and subsequently obtain a list or collection of websites (e.g., URLs) from the one or more search services 18 corresponding to or matching the passed scenario parameters. Of course, the search services 18 are not limited to web feed aggregators and may in other embodiments include more traditional search engines and/or the like.

In any case, the query manager 56 may perform queries for open source information (e.g., posts such as articles, blog entries, etc.) that matches one or more sets of scenario parameters for various users according to any desired (e.g., automated) schedule (which may be configured via dashboard 346). In one arrangement, the query manager 56 may perform a query of one or more of the search services 18 each morning such that the most recent or substantially most recent news articles, blog entries, etc. may be available to a user (e.g., via dashboard 346) at the beginning of the day. Of course, numerous other query schedules are envisioned which may be automatically and/or manually performed. In any event, the query manager 56 may obtain from the search services 18 identifying information for a number of search results (e.g., URLs) which may be stored in data store 46 and/or utilized by the collection manager 58 as will be discussed below.

With continued reference to FIG. 2, the collection manager 58 may include a retrieval module 66 that may function to actually retrieve the open source information (e.g., the source code of a particular webpage of a website) via the URL or website identifying information obtained by the query manager 56, and a content extraction module 70 that, as will be discussed below, can extract desired content (e.g., the substantive text of a news article and not advertisements, navigation sections, etc.) from the particular webpage or other online data source for use in subsequent filtering and analyses. While the content extraction module 70 and related protocols (e.g., protocol 98 illustrated in FIG. 12) will be discussed in the context of extracting desired content from the source code of webpages and/or other online open source data, it is envisioned that the content extraction module 70 and related protocols may also be used to extract one or more types of content from other types of data as well (e.g., an organization's internal data, financial data, etc.).

With additional reference now to FIG. 9, content extraction module 70 may include a parsing module or parser 74 that is operable to parse source code of a particular webpage or online data source into a number of elements and an extraction engine 78 that is configured to extract one or more type of content from the source code on which one or more types of analyses can be performed. A representative piece or segment of code 76 (e.g., HTML code) is illustrated in FIG. 10 that includes a number of elements 77, where each element 77 is associated with at least one tag 79 (for clarity, only some of the elements and tags have been labeled). The parser 74 may parse the code 76 into a hierarchical parse tree 80 as illustrated in FIG. 11, where the parse tree 80 includes a number of nodes 81 and each node 81 represents one of the elements 77 of the code 76.

The extraction engine 78 may also include a tag type determinator 82, a heuristic score module 86 and an object generator 90 which collectively function to extract one or more desired types of content from the source code of the particular webpage being analyzed through a heuristic (e.g., learning) process that requires little or no prior knowledge of the particular webpage (and with little or no human interaction). The extraction engine 78 may process the nodes 81 of the parse tree 80 in any appropriate orderly fashion (e.g., all sibling nodes, and then all sibling nodes of the next lower level, etc.) to determine whether each node is or is not likely to include content of interest.

As will be discussed below, part of this process may include utilizing the tag type determinator 82 to determine the tag type of the node (e.g., “HTML a” tag, “HTML text” tag), and then utilizing the heuristic score module 86 (which makes a number of queries in relation to the tag type and other node features) to assign a “heuristic score” to each node that is at least partially indicative of an interest level of the content of the node. For instance, lower scores (e.g., −1, −2, etc.) may indicate that the content of the node is more likely to be substantive (e.g., the actual text of a news article or blog entry) and thus of greater interest to a user in subsequent searches or analyses of the content (e.g., filtering, sentiment analyses, hierarchical signature analyses). As another example, higher scores (e.g., 1, 2, 3, etc.) may indicate that the content of the node is less likely to be substantive and thus less likely to be of interest to a user for subsequent searches or analyses. Advantageously, the extraction engine 78 may “fine tune” the score of a particular node over time by way of making further inquiries in relation to a node and or its features (e.g., attributes, events, content, etc.) to lend further confidence to the interest level of the content of a particular node. Once the extraction engine 78 has completed processing of the nodes of the parse tree 80 of a particular piece of source code, the object generator 90 of the extraction engine 78 is operable to generate one or more objects (e.g., data structures) that include the content of interest (e.g., the content of nodes with lower heuristic scores) which may be appropriately indexed (e.g., via URLs) and stored in data store 46.

As shown in FIG. 12, a protocol 98 (e.g., one or more sets of computer readable instructions) is illustrated that is operable to extract desired content from source code of a webpage. It should be understood that extraction engine 78 and its respective modules (e.g., tag type determinator 82, a heuristic score module 86 and an object generator 90) may not necessarily represent physical pieces of hardware, but may merely represent particular segments of the protocol 98 that collectively function to extract content from source code of a webpage and generate corresponding objects. For instance, the retrieval module 66 may represent the step of obtaining 102 source code for generating at least one website or webpage in FIG. 12, and the parser 74 may represent the step of parsing 106 source code to obtain a parse tree in the protocol 98 in FIG. 12. Similar discussion applies to other modules, engines, and the like disclosed herein.

The protocol 98 may begin by obtaining 102 source code used to generate at least one website (e.g., the source code 76 shown in FIG. 10) from any appropriate data store (e.g., data store 46). After the source code is parsed 106 to obtain a parse tree (e.g., the parse tree 80 shown in FIG. 11), a tag type of a node (e.g., node 81) in the parse tree may be determined. For instance, the protocol 98 may begin with a node under a root node of the parse tree (e.g., one of the nodes 81 directly under the root node) and any child nodes of the node (i.e., lower nodes in the parse tree off of the node being currently analyzed). Of course, the nodes may also be analyzed in other appropriate manners. Once the tag type of the node is determined 110, it may be determined 114 whether it is an “HTML a” tag (i.e., an anchor that may be used to establish a link to another document or a bookmark on a page). Nodes 81 having such tag types may indicate that the content of such nodes is directed to links/bookmarks (instead of substantive text of a webpage) and thus may not be useful in a subsequent search and/or analysis of the webpage.

In response to an affirmative answer to the inquiry at 114, a first heuristic score (e.g., a score greater than 0) may be allocated to or associated with the node (e.g., where a negative answer to the inquiry at 114 may result in a second heuristic score less than zero) and the protocol 98 may then query 154 whether the tag type lacks an “href” attribute or includes an href attribute starting with “#”.

An affirmative answer to this inquiry 154 may indicate 158 that the content of this particular node is likely not of interest (i.e., is not directed to substantive content of the webpage because it includes a hyperlink to another portion of the same webpage). For instance, the first heuristic score may assume a third heuristic score (e.g., 2) when the inquiry at 154 is affirmative. Assuming the third heuristic score indicates that the content of the node is likely not of interest, then the node and any child nodes of the node may then be deleted 162 from the analysis, and then the protocol 98 may query 130 whether there are additional nodes to process. This process of determining when a particular heuristic score indicates deletion of a node will be discussed in more detail below. In any event, if the inquiry 130 indicates that there are additional nodes to processes, the protocol 98 may then flow back to 110 to determine a tag type of a node as discussed previously. For instance, processing may move to a “sibling” node of the previously processed node (i.e., a node at the same hierarchical level of the parse tree 80). As another example, any offspring or child nodes of the node may be processed (e.g., starting at box 110), and the heuristic score of each child may be the heuristic score of its parent plus the heuristic score of the child determined in isolation from other nodes.

In any event, and returning to inquiry 154, if the tag type of the node was determined 154 to not lack an href attribute or not include an href attribute beginning with “#”, then the first heuristic score may assume a fourth heuristic score (e.g., less than the third heuristic score and greater than the second heuristic score, e.g., 1) and the protocol 98 may make a determination 142 that the node content may be of interest and may perform 146 additional processing on the node (i.e., make additional determinations of the tag type of the node which lend further confidence that the node is or is not of interest). For instance, if the content of the node is a link to another website (i.e., is an “inlink”), such content may be useful for building an online information flow network as will be discussed later in this discussion. As another example, the additional processing may query whether the tag type is an “HTML img” tag, and, if so, allocate a particular heuristic score to the node (e.g., 0). As a further example, the additional processing may entail determining whether the tag type is an “HTML li” tag (i.e., a list tag), and then assign a particular heuristic score to the node based upon the relative interest in the content of a node having such a tag.

Returning to 114 where it was queried whether the tag type of the node is an HTML a tag, a negative answer to this inquiry may cause the protocol 98 to allocate a second heuristic score to the node (e.g., less than 0) and make a further inquiry as to whether the tag type of the node is an “HTML text” tag at 118. A positive determination at block 118 may cause the second heuristic score to assume a third heuristic score (e.g., −1) and cause an indication 122 that the content of the particular node is likely of interest (i.e., because it appears, by virtue of its tag type being a “text” tag, that the content of the particular node at least partially makes up a substantive portion of a webpage, e.g., the text of a news article rather than an advertisement section), and then the node content may be extracted 126 for further processing. However, a negative determination at 118 may cause the second heuristic score to assume a fourth heuristic score (e.g., 0), and then the protocol 98 may flow to 142 and 146 for additional processing on the node as discussed previously.

Once heuristic scores have been allocated to the various nodes of the parse tree, numerous manners are envisioned for determining whether the content of a particular node is to be extracted for use in generating an object or whether the node (and any child nodes) is to be deleted (i.e., not extracted for use in building an object). In one arrangement, if the node is a list node (e.g., see above discussion in relation to additional processing at 146) and has a heuristic score of greater than −1, then the node and any children nodes may be deleted. In another arrangement, if the node has one or more children and has a navigation heuristic score that is greater than 0, then the node and any children nodes may be deleted. In another arrangement, the context of any node with a heuristic store of less than −2 may be extracted. In further arrangements, nodes may be retained and/or deleted based on tag type (e.g., without regard to heuristic score) or based on heuristic score (e.g., without regard to tag type).

In some situations, a website or URL obtained by the retrieval module 66 may include a plurality of articles, only one of which was the reason the website was obtained by the query manager 56 from one or more of the search service 18. For instance, in the situation where a search service 18 is a web feed aggregator and returns a list of URLs with a summary of the relevant article(s) or posts(s) in each returned URL, various words or terms of the summary can be used by the protocol 98 or content extraction module 70 for extracting just the substantive text of the particular article as opposed to the substantive text of all of the articles or posts on the website.

It should be understood that the use of “first” heuristic score, “second” heuristic score, etc. has only been used for purposes of discussion and should not in any way limit the scope of the disclosure. Rather, such labels have merely been used to explain the various types of relationships between heuristic scores based upon the answers to various inquiries about the nodes of a parse tree.

Once it has been determined 130 that there are no additional nodes to process, then the protocol 98 may generate 134 an object 94 (e.g., any appropriate data structure, see FIG. 9) that includes the interesting content of the nodes (e.g., just the text of a news article), and then the object may be sent to a data store (e.g., data store 46 in FIG. 1) for use in subsequent searches and/or analyses (e.g., by tools of toolbox 62 in FIG. 2). With reference to FIG. 13, a representative object 136 (e.g., object 94) is shown including content 137 extracted from the source code of an online data source 138 (e.g., a news article) using the content extraction module 70 (e.g., protocol 98).

Returning to FIG. 3, the dashboard 346 may include a post query administrator 354 that is operable to accept any appropriate query parameters (e.g., key words, Boolean operators, date ranges, etc.) from a user (e.g., via any appropriate peripheral device) and then coordinate with the data access layer 54 of the WISDOM server 14 to filter or perform a query of the objects 94 stored in data store 46 corresponding to one or more scenarios based on the accepted query parameters. In this regard, the post query administrator 354 can allow a user to define one or more “sub-scenarios” of one or more previously defined scenarios. As discussed throughout, a “post” may be a news article, individual blog or forum entry, and/or other online data source. Upon receipt of query results (e.g., objects 94) from data store 46, the post query administrator 354 may cause the presentation of such search query results on a user's display (e.g., a list of the results in any desired order such as by relevancy, date, type of post, etc.).

With reference now to FIG. 14, another screenshot 404 of the dashboard 346 is illustrated that may be presented on a display by the post query administrator 354 upon manipulation of a “post search” button 410. This screenshot 404 allows a user to define a search or query to be performed by data access layer 54 and/or post query administrator 350 on objects 94 in data store 46 corresponding to one or more particular scenarios (and then receive corresponding search results). This screenshot 404 may include a navigation section 408 having a number of buttons 410 (or other user manipulable features), each of which provides a user access to a particular feature or features of the WISDOM server 14 (e.g., sentiment analysis, hierarchical signatures, etc.). The navigation section 408 may also include a control panel 412 including one or more user manipulable features (e.g., typing cells, drop down menus, etc.) that allow a user to modify or control query or analysis parameters (e.g., search terms, date ranges, type of post to be returned, etc.). The screenshot 404 may also include a presentation area 416 for presenting a graphical representation of search results, analyses, and the like, depending upon the particular button 410 (or other manipulable feature) manipulated.

For instance, the control panel 412 may include a cell 420 that allows a user to enter one or more keywords and/or Boolean operators (e.g., “hostage OR otage OR kidnap OR ransom”) on which a query of objects 94 is to be performed. The control panel 412 may also include cells 424 to enter or select a time period during which returned search results must fall within (e.g., as determined by their publication dates), a drop down menu 428 to select the particular type of post that the returned search results must be (e.g., blog posting, news article, etc.), and/or a drop down menu 432 which allows a user to select a maximum number of search results to return.

Returned search results may be presented (e.g., in list form) in the presentation area 416, where each search result may include a link (e.g., a URL) to the source of the search result (e.g., to the website on which a news article is found), a summary of the post, the type of post (e.g., blog post, news article), among other information (e.g., number of in-links to post). In one arrangement, the post query administrator 350 governs presentation of the search results on the user's display (i.e., data related to the search results are received from the WISDOM server 14, and then the post query administrator 350 converts the data into the graphical representation shown in the presentation area 416 as shown in FIG. 14). While not shown, a user may also be able to set up a number of different queries (each being defined by different query parameters) according to one or more query schedules. For instance, a “Query A” may be set to run on the objects 94 of a particular scenario twice a day whereas a “Query B” may be set to run on the objects 94 of a different scenario once per morning. Query results may be stored in data store 46 of WISDOM server 14 and made accessible to a user on client device 22 via data access layer 54 of the WISDOM server 14. Of course, query results may also be stored on storage module 334 of client device 22 (e.g., via data export manager 358 of dashboard 346). With reference now to FIGS. 2 and 15, the toolbox 62 of the backend processing engine 50 may include any appropriate number of modules, engines and the like that are operable to retrieve objects 94 (where each object 94, as discussed above, represents desired content (e.g., substantive content) of an online data source such as a news article, blog posting, and the like obtained by backend processing engine 50 in a query of search services 18 based on one or more scenarios) from the data store 46 in relation to one or more scenarios and then perform one or more types of analyses on such objects for use in conveying additional/enhanced visual analytics to users. For instance, one of the tools of the toolbox 62 may be a sentiment analysis engine 166 for use in automatically determining a “sentiment” of one or more terms among one or more data sets (e.g., objects 94) over any appropriate time period(s). In one embodiment, each data set represents the objects 94 corresponding to one or more particular scenarios or sub-scenarios.

As used herein, a “sentiment” of a term or phrase may be an impression (e.g., negative, neutral, positive) of the term or phrase based on the general context of the object(s) 94 in which the term is found. The sentiment analysis engine 166 may allow a user who has defined a scenario (e.g., via scenario generator 350 of dashboard 346, see FIG. 3) to be used in obtaining online open source information (e.g., news articles, blog entries) to visualize a sentiment and/or volume of the “x” (where x may be any positive integer) most frequently disclosed terms and/or phrases (e.g., top 5, top 10) over a time period (e.g., over the past 2 weeks) in the returned open source information corresponding to the user's scenario(s). For instance, a user who has defined a scenario centered on recent attitudes or opinions of President Obama in relation to healthcare may obtain a graphical representation of a sentiment and volume of terms such as “Obama,” “Medicare” and “pharmaceutical” based on returned open source information corresponding to the defined scenario. In one arrangement, the sentiment analysis engine 166 may automatically select those terms to be used as part of a sentiment/volume analysis (e.g., x most frequently disclosed) instead of the user having to manually select words or terms for which to perform a sentiment analysis. It is noted that the words/terms may or may not be the same as the scenario parameters used by the query manager 56 to obtain corresponding open source information.

As shown in FIG. 16, the sentiment analysis engine 166 may include a frequency analyzer 190 which is operable to receive or retrieve data sets 186 (e.g., objects 94 corresponding to one or more scenarios or sub-scenarios) and determine the x most frequently disclosed terms among the data sets 186 (where “x” is a positive integer). The frequency analyzer 190 may pass the x most frequently disclosed terms (and possibly the objects in which such terms were disclosed) to a sentiment determinator 194 and a volume determinator 198 for respectively determining a sentiment and volume of each of the x most frequently disclosed terms over a particular time period and thereafter generating data 202 for use in generating a graphical representation on a display in relation to the sentiments/volumes of the x most frequently disclosed terms. In one arrangement, the data 202 may be passed to data store 46 of WISDOM server 14 and passed to or retrieved by dashboard 346 for presentation of the sentiment/volume information on a display.

The sentiment analysis engine 166 may be operable to automatically update the sentiment/volume analysis upon any scenario or query parameters being modified by a user and/or new online data being received by backend processing engine 50. For instance, upon a user choosing to analyze objects 94 of a different scenario (e.g., via dashboard 346), the sentiment analysis engine 166 may automatically cause the recalculation of the sentiment/volume of the x most frequently disclosed terms based on the objects of the different scenario.

As shown in FIG. 17, a protocol 210 (e.g., one or more sets of computer readable instructions) is illustrated that is operable to determine a sentiment and volume of one or more terms of one or more data sets (e.g., objects 94) and then present or cause the presentation of a graphical illustration of the sentiments and volumes on a display. As discussed previously, each component of the sentiment analysis engine 166 may represent one of more steps or portions of protocol 210. The protocol 210 may begin at 214 by receiving the x most frequently disclosed terms from a plurality of data sets during a time period. As discussed previously, the data sets may be in the form of objects (e.g., objects 94) representing the source code of websites and/or other online data sources returned in response to a user's search query. The protocol 210 may then determine 218 whether any of the x most frequently disclosed terms is a “stop term”. As used herein, a “stop term” (e.g., a, an, the) is a term that, when matched by one of the x most frequently disclosed terms, is automatically removed from further analysis and replaced with the next most frequently disclosed term that is not a stop term. Such stop terms may be automatically determined or set by the sentiment analysis engine (i.e., there may be default stop terms) and/or may be manually selected by a user (e.g., via dashboard on client device 22). Thus, a term may be replaced with the next most frequently disclosed term at 222 in response to a positive determination at 218.

Turning briefly to FIG. 27, another screenshot 508 of the dashboard 346 is illustrated after a “Scenario Admin” button 410 has been manipulated. In this screenshot 508, one portion 512 may allow a user to specify one or more of stop or ignore words that are to be ignored during processing at the WISDOM server 14 (e.g., during a sentiment analysis). In this regard, the scenario administrator 378 of the dashboard 346 would communicate with the sentiment analysis engine 166 to limit a sentiment analysis from being performed on a stop word specified in portion 512. Returning to FIG. 17, the protocol 210 may eventually proceed to 226 whereby the sentiment and volume of each of the x most frequently disclosed terms among the data sets during the time period is determined. In relation to determining the sentiment of a term among a number of data sets (e.g., objects 94) disclosing such term, numerous manners of such determination are envisioned. In one arrangement, it may first be determined, for each of the websites or online data sites (and/or their objects 94) disclosing the x most frequently disclosed terms, whether the data site (or its object) is a positive, negative or neutral data site. This may be accomplished (either at the post/article level or at the sentence level) by mining the object for positively charged words (e.g., esteemed, great, liked) and negatively charged words (e.g., hate, coup, overthrow), and then using the totals to determine whether the object (i.e., the website) is a positive, neutral or negative site. For instance, if the text of such an object contains 20 instances of “esteemed” but only 5 instances of “defunct,” then the website may be afforded a “positive” label. It is also envisioned that some of the charged words or terms may be afforded more or less weight than others (e.g., the term “kill” may be afforded twice as much weight as the term “hate” in the positive/neutral/negative website determination process).

In any event, the step 226 of determining the sentiment of each of the x most frequently disclosed terms may include summing the number of positive data sites disclosing the term to obtain a count of positive data sites, summing the number of negative data sites disclosing the term to obtain a negative count of data sites, subtracting the count of negative data sites from the count of positive data sites to obtain a result, and using the result to obtain the sentiment of the term over a particular time increment (e.g., day) of a particular time period (e.g., week). In one arrangement, a negative result indicates a negative sentiment, a positive result indicates a positive sentiment, and a result of zero indicates a neutral sentiment. In another arrangement, a result of less than −2 indicates a negative sentiment, a result of greater than 2 indicates a positive sentiment, and a result of between −2 and 2 indicates a neutral sentiment. For example, if a term appears in 10 negative articles and in 4 positive articles, the overall sentiment may be negative. Other manners of determining term sentiments are also envisioned.

A similar procedure may be performed 230 for other terms and/or additional time increments of a time period (e.g., for additional days of a one week time period) for each of the terms. In relation to determining the volume of a term among the data sets during a time increment, the total number of data sites/articles/posts mentioning the term during the time increment is summed. In one arrangement, the frequency of the term in each data site/post/article may not be taken into account to limit the bias that may result from a length of the post/article. Any analytical data resulting from the various processing steps may be appropriately stored in data store 46.

Once the processing has completed for the various terms over the various time increments and/or periods, a graphical representation of the volumes and sentiments of the x most frequently disclosed terms may be presented 234 on a display of a client device 22. For instance, the dashboard 346 may include a sentiment module 362 (see FIG. 3) that is operable to obtain data from data store 46 of WISDOM server 14 related to term sentiments and volumes (as generated by the sentiment analysis engine 166) and present one or more corresponding graphical representations of such information on a display.

Turning to FIG. 18, another screenshot 444 of the dashboard 346 may be presented to a user upon manipulation of a “Keywords” button 410 that conveys sentiment and volume information for one or more terms and/or phrases found in objects 94 of one or more scenarios or sub-scenarios. As shown, the presentation section 416 in this screenshot 444 may include a number of cells or portions 448, where each portion 448 may present a graphical representation (e.g., sparkchart) of sentiment/volume information for a particular term.

For instance, each portion 448 may include a series of lines or bars 452, where each bar 452 represents a particular day (e.g., an x-axis of the series represents days), a height of the bars (e.g., a y-axis of the series) represents relative volume, and a color of the bars (and/or other feature of the bars such as surface texturing, shape, etc.) represents sentiment. In one arrangement, a green color of a bar 452 may indicate a positive sentiment for the particular term for the particular day, a red color of a bar 452 may indicate a negative sentiment for the particular term for the particular day, and a gray color of a bar 452 may indicate a neutral sentiment for the particular term for the particular day. Of course, numerous other arrangements are envisioned for presenting the sentiment and/or volume of a particular term to a user.

This screenshot 444 may also include a number of buttons 456 or other user manipulable features that allow a user to modify and/or analyze the terms in the portions 448 shown in the presentation area 416. For instance, a user may be able to initially select a desired group of terms in any appropriate manner (e.g., by clicking or selecting a checkbox (not labeled) in the portion 448 of a particular term). Thereafter, and upon selecting a “Compare” button 456, the sentiment module 362 may function to automatically filter the portions 448 illustrated in the presentation area 416 such that only the selected terms may presented for comparison of their respective sentiments and volumes.

As another example, a user may be able to select a “Top 5 Keywords” button 456 such that portions 448 corresponding to the top five most frequently disclosed terms among the posts/articles/data sites returned matching a particular scenario are shown in the presentation area 416. As discussed previously, this feature limits the need for a user to manually review the search results for terms on which to perform sentiment and volume analyses. Furthermore, a user may be more interested in reviewing sentiment/volume analyses for terms that are more frequently disclosed than other terms as the mere fact that the term is frequently disclosed may indicate a greater relative importance of the term in relation to other terms.

As discussed previously, a user may specify one or more “stop words” that may not be taken into account during a sentiment analysis (see previous discussion in relation to FIG. 27). As also discussed previously, updating/revising a scenario (e.g., via changing one or more scenario parameters) and/or updating/revising filtering parameters (e.g., via post query administrator 354) may cause the various graphical representations in the portions 448 to automatically adjust/change as necessary to reflect a current sentiment/volume of the terms. In one arrangement, and although not shown, one or more graphical representations/sparkcharts providing sentiment/volume analysis for one or more terms may be presented (e.g., discretely) on a website of one of the returned search results (e.g., upon a user clicking or selecting a link to a website in the screenshot 404 of FIG. 14).

With reference now to FIGS. 15 and 19, another of the tools of the toolbox 62 of the backend processing engine 50 may be a signature engine 170 that is broadly operable to create one or more “hierarchical signatures” for a web or online data site for allowing a user to, for instance, discern the ebb and flow of topics over any appropriate time period on individual websites as well as on automatically clustered sites having similar signatures. More specifically, a “signature” of a website or other online data source may be obtained by determining a frequency or prevalence of particular terms on one or more pages of the website over a time period, and then appropriately presented on a display for visualization by a user. For instance, a frequency of each of the terms “countertenor,” “government,” “military,” and “president” on each of a number of websites (e.g., those websites obtained from search services 18 by backend processing engine 50 that correspond to a particular defined scenario) may be determined, the results may be normalized to “high,” “medium” and “low,” and then such normalized results may be presented for a user on a display in the form of a color coded chart for one or more of such websites (e.g., where darker colors represent higher frequency and lighter colors represent lower frequency). This utility may allow such signatures to be leveraged to track discussions, infer textual linkages among websites, discover communities of interest according to topic saliency, and the like.

As shown in FIG. 19, the signature engine 170 may include a frequency analyzer 242 that is operable to receive one or more data sets 238 (e.g., objects 94 obtained from data store 46) and determine a frequency or prevalence of each of a number of particular terms from the data sets 238. For instance, the frequency analyzer 242 may determine the prevalence of one or more terms of at least one textual hierarchy that includes at least first and second level terms, where each first level term is a textual category and each second level term is a term encompassed by at least one first level textual category. A signature determinator 246 may then perform second level hierarchical signature processing 250 and first level hierarchical signature processing 254 to obtain a hierarchical signature object 258 for a particular web or online data site that is essentially represented by the particular prevalence of a number of specific terms in object representing the particular web or online data site. The web site signature object 258 may be passed to data store 46 and retrieved by a dashboard of a user's client device 22 which may operate to present a representative graphical illustration of the signature(s) on the user's display.

As shown in FIG. 20, a protocol 266 (e.g., one or more sets of computer readable instructions) is illustrated that is operable to determine a hierarchical signature of one or more websites and/or communities of websites and then present a graphical representation of such hierarchical signature on a display. As discussed previously, the various components of the signature engine 170 may represent one of more steps or portions of protocol 266. The protocol 266 may begin by identifying 270 at least one textual hierarchy having first and second levels. In one arrangement, a user may be presented with a number of predefined textual hierarchies that may be selected by the user via the dashboard 346 (e.g., see portion 516 in screenshot 508 of FIG. 27) and/or may define additional textual hierarchies. For instance, a first textual hierarchy could include a first level term of “Government” and corresponding second level terms of “Congress,” “Senate,” “President,” and “Constitution” while a second textual hierarchy could include a first level term of “Sports” and corresponding second level terms of “football,” “soccer,” “basketball,” and “tennis”. In one arrangement, the backend processing engine 50 may automatically choose terms for a textual hierarchy based at least in part on the scenario parameters used by a user to define a particular scenario; doing so may aid in presenting to a user hierarchical signatures of websites matching a particular scenario (or sub-scenario) that may be of greater interest to the user (compared to the textual hierarchies made up of randomly selected terms and/or terms having higher disclosure frequencies in website objects than other terms).

In any event, the protocol 266 may proceed to determine 274 a number of occurrences of each of the second level terms of the at least one textual hierarchy in an object 94 corresponding to a particular returned post or website of a defined scenario for a particular time period (e.g., for a day of a 3 week time period), and then obtain (utilizing the determined number of occurrences of each second level term) a hierarchical signature of each of the second level terms representing a prevalence of each term on the particular website during the time period. In one arrangement, the hierarchical signature of each second level term may be obtained by dividing the number of occurrences of the term by the number of pages of the particular website on which the term is found to obtain the hierarchical signature for the at least one term for the particular website. For instance, if the second level term “computer” was found 100 times across 25 pages of a website on a particular day, then the hierarchical signature for “computer” for the day would be four. Furthermore, some second level words or terms of the textual hierarchies may be weighted more than other second level terms when merely a single use of such term could be highly representative of the content of the website/blog posting as a whole.

Once the second level signatures have been obtained at 278, the protocol 266 may then utilize the second level hierarchical signatures to obtain 282 a first level hierarchical signature of the at least one textual category that encompasses the various corresponding second level terms. In the case where a first level textual category encompasses just a single second level term, the hierarchical signature of the first level textual category would be that of the second level term. In the case where the first level textual category encompasses a plurality of corresponding second level terms, the hierarchical signature of the second level textual category may be obtained by, for instance, averaging the hierarchical signatures of the plurality of second level terms (and/or performing other types of statistical analyses).

Once the first and second level hierarchical signatures have been determined, then one or both of such signatures may be utilized 286 to establish a hierarchical signature for the particular website. In one arrangement, the first and second level hierarchical signatures may be obtained for the particular website using a plurality of textual hierarchies. In this regard, the hierarchical signature for the website may be the combination of the first and second level hierarchical signatures for the plurality of textual hierarchies. In any event, if it is determined at 290 that additional analyses for additional time periods and/or textual hierarchies are required, the protocol may flow back to 270 to identify one or more textual hierarchies. Any analytical data resulting from the various processing steps may be appropriately stored in data store 46. Of course, a similar analysis may be performed for additional posts or websites.

In another arrangement, any appropriate algorithm for or manner of discovering at least one website community may be used to obtain at least one website community from a plurality of websites, and then the hierarchical signatures of the websites making up the website community may be utilized (i.e., they may be averaged or otherwise “rolled up”) to obtain a hierarchical signature for the website community.

In any event, one or more graphical representations of various hierarchical signatures may subsequently be presented 294 on a display for visualization by a user. Turning now to FIG. 21, another screenshot 460 of the dashboard 346 may be presented to a user upon manipulation of a “Signatures” button 410 that illustrates such graphical representations. Here, a signature module 366 of the dashboard 346 (see FIG. 3) may function to retrieve hierarchical signature data for one or more web or data sites from data store 46 of WISDOM server 14 (as generated by signature engine 170 of WISDOM server 14) and present a graphical representation of such one or more hierarchical signatures on a user's display. The websites for which a hierarchical signature is determined may be either those websites matching a particular scenario (e.g., as coordinated by scenario generator 350, query manager 56, etc) and/or a particular sub-scenario (e.g., as coordinated by post query administrator 354). In some arrangements, the signature module 366 may automatically determine those signatures to be displayed in the presentation area 416 in any appropriate manner (e.g., by date, relevancy, etc.). In other arrangements, a user may manually select the particular hierarchical signatures to be displayed.

In any event, the presentation area 416 may include a number of portions 468, where each portion 468 may present a graphical representation (e.g., sparkchart) of a hierarchical signature for a particular web or data site. For instance, each portion 468 may include a series of lines or bars 472, where each bar 472 represents a first level textual category of a textual hierarchy. A user may select particular textual categories and corresponding terms to be used for determining hierarchical signatures in portion 516 of screenshot 508 in FIG. 27.

Each bar 472 may be appropriately textured, colored, and/or the like to indicate a relative prevalence of a particular first level textual category on a particular website. In some arrangements, one or more of the hierarchical signatures may be normalized (e.g., by the signature engine 170 and/or signature module 366) to allow, for instance, the intensity of a particular hierarchical signature to be represented as “high,” “medium,” “low,” etc. instead of or in addition to a numerical representation. For example, in the context of a first level textual hierarchy encompassing a plurality of second level terms, the normalizing may include ascertaining a mean and standard deviation of the hierarchical signatures of the second level terms, subtracting the mean from each of the second level term hierarchical signatures, and dividing each of the values resulting from the subtracting by the standard deviation to obtain z-scores for each of the first and second term hierarchical signatures. In this case, the graphical representations of the second level term hierarchical signatures would respectively correspond to the z-scores of the second level term hierarchical signatures. In one arrangement, a first color (e.g., a darker color) of the graphical representation could represent a first prevalence of the at least one term and/or at least one textual category on the at least one website and a second color (e.g., lighter color) of the graphical representation could represent a second prevalence of the at least one term and/or at least one textual category on the at least one website, where the first prevalence is higher than the second prevalence. A similar procedure may be performed for the first level textual category hierarchical signatures.

For instance, a darker color (e.g., blue) of a bar may indicate a higher prevalence of the first level textual category on the website while a lighter color (e.g., white, gray) may indicate a lower prevalence of the first level textual category on the website. In one arrangement, moving a user manipulable device (e.g., cursor, finger) over a particular bar 472 causes the presentation of a pop-up box or tooltip 476 having a visual indication as to the normalized prevalence of the particular first level textual category (e.g., “government-average”).

As shown, this screenshot 460 may include a number of buttons 464 or other user manipulable features that, when manipulated, allow a user to toggle between site signatures and community signatures. As discussed previously, a signature of any appropriately defined or determined “website community” may be determined by “rolling up” the signatures of the individual websites making up the community.

Turning now to FIG. 22, another screenshot 480 of the dashboard 400 is shown upon the “community signatures” button 464 being manipulated. In this screenshot 480, the presentation section 416 may include a number of portions 484, where each portion 484 may present a graphical representation (e.g., sparkchart) of a hierarchical signature for a particular community. Each portion 484 may include an expand button 488 that, when manipulated, may cause the display of the various websites making up the particular community. Additionally, each portion 484 may include a “time” button 492 or other type of user manipulable feature that, when manipulated, may cause the display of a pop-up window or other type of view that illustrates hierarchical signatures for a community for each of a number of time increments of a time period (e.g., for each day of a 4 month time period).

With respect to FIG. 23, a pop-up window 496 may present a “time signature” for a community on a user's display upon manipulation of a time button 492 corresponding to the particular community. The pop-up window 496 may include a plurality of portions 500, where each portion 500 represents a hierarchical signature for the community for a particular time increment (as shown, for a particular day). Each portion 500 may include a number of lines or bars 504, where each bar 504 represents a first level textual category of a textual hierarchy, and where a color of each bar represents a particular prevalence of the first level textual category in the community (similar to those shown in FIGS. 21-22). Furthermore, each of the first level textual categories may be associated with an expand button 508 that, when manipulated, causes the display of a number of lines or bars 504 representing the prevalence of each of the second level terms of the particular first level textual category. Although not shown, time and expand buttons may also be provided for site signatures (e.g., in screenshot 460 of FIG. 21).

With reference again to FIG. 15, another of the tools of the toolbox 62 of the backend processing engine 50 may be an information flow network extraction engine 174 that is broadly operable to infer one or more online information flow networks among a plurality of online data sources (e.g., individual blog or forum entries on website, news articles, webpages and/or other posts, which may be those obtained by backend processing engine 50 that correspond to a particular scenario) which may then be presented in the form of a graphical representation on a user's display for visualization by the user. Such graphical representations may illustrate information flows from “primary” data sites or sources (e.g., authors, news articles, etc.) to “secondary” data sites or sources over time. Over time, a more robust picture of each person, actor, author, news article, and the like discussing a topic may be built to better identify differences between insignificant/spurious relationships and more significant relationships across various demographics, cultures, and the like. Advantageously, companies and other brand management functions can readily observe who is saying what about their products, services, and the like. Furthermore, analysts can observe and understand the significance of relationships between authors, articles, and the like from what is often noisy and complicated open source data.

As shown in FIG. 24, a protocol 298 (e.g., one or more sets of computer readable instructions) is illustrated that is operable to infer or extract an online information flow network from a number of online data sources. For purposes of this discussion, an “online data source” may be a news article, one or more individual blog or forum entries or postings, and the like. An online data source may be found on a website, one or more webpages of a website, and the like.

In the case of, for instance, a news article found on one or more pages of a website, the news article may be associated with a unique URL that allows a user, process, module, etc. to locate the article over any appropriate network (e.g., the Internet). Such news articles and other online data sources may refer to other online data sources via hyperlinks (e.g., inlinks) within the source code of the online data sources (where the referred to online data source may be a “primary” data source and the referring online data source may be a “secondary” data source). Unique URLs for primary and secondary data sources may be found, for instance, in “information” related to source code used to generate the news article or online data source on the webpage (e.g., an object 94 related to the source code, the original source code for the webpage, etc.).

Some online data sources may not be associated with unique URLs that specifically identify the online data sources. For instance, in the case of an individual blog or forum entry, there may not be a unique URL available to link directly to the individual entry or posting; rather, there may only be a unique URL available for the website or webpage as whole where a number of entries or postings are found (where a number of entries may be related by a common topic or subject). In the latter case, each entry or posting may be associated with any appropriate identifier used by the webmaster of the website to differentiate between the various postings. However, such identifiers may not uniquely identify an individual entry or posting in relation to other online data sources. In this regard, and as will be discussed in more detail below, the protocol 298 may be able to construct or obtain a construction of a unique URL for each individual posting or entry based on a combination of the URL of the website where the entry is found plus additional information (e.g., the identifier of the entry, the topic within which the entry is found, etc.).

The protocol 298 may begin by receiving 302 “information” related to source code portions used to generate online data sources. For instance, such information may be objects (e.g., objects 94) for a number of online data sources generated in response to the query manager 56 processing a particular scenario. As discussed previously, the content extraction module 70 may function to generate objects from the source code of webpages returned by the query manager 56 that include content of interest such as the substantive text of a news article or blog entry, any links within such substantive text to other online data sources, and the like (instead of advertisements and related links, navigation sections, etc.).

Once the information has been received 302, the protocol 298 may then determine 306 whether any of the received online data sources refer to other online data sources during a plurality of time periods from the received information. In the case of an article or other posting on one or more pages of a website, this may entail scanning the information (e.g., the object 94) for any links (e.g., URLs) within the substantive content of the article or posting to other online data sources. In the case of a blog or forum entry, this may entail determining whether the entry was posted in response to or off of a previous entry. In any case, the protocol may then determine 310 whether unique URLs that identify both the secondary data source (i.e., the referring data source) and the primary data source (i.e., the referred to data source) are available in the information, and then extract 314 the unique URLs from the information in response to a positive determination at 310.

If unique URLs for the primary and second data sources are not (directly) available from the information, then the protocol may proceed to construct 318 (or obtain a construction of) unique URLs for the primary and/or secondary data sources. For instance, in the case of a blog entry, a unique URL may be constructed for use by the online information flow network engine 174 (e.g., the protocol 298) in building online information flow networks by way of combining a URL of the website or webpage where the blog entry is found with another piece of information (e.g., an identifier of the particular blog entry, the topic within which the blog entry was found on the website, etc.) in any appropriate manner. The above process of extracting or constructing unique URLs for a number of online data sources may be performed during each time increment of any desired time period(s) (e.g., for each day of a two week time period). Any analytical data resulting from the various processing steps may be appropriately stored in data store 46.

Once an initial set of relationships have been determined, other existing public data sources may be appropriately leveraged to add confidence to the existing discovered relationships (as well as possibly identify new ones). For example, online information flow extraction engine 174 may search a blog for all posts and comments made between an author and specific actors that were previously discovered. Depending on the volume and type of other relationships discovered, a certain level of confidence could be added to the original set of relationships. An individual, community or demographic tolerance can be provided or calculated on-the-fly to determine how much support is sufficient to label a relationship as “significant”. In one example, one particular online actor may be found who comments on a significant number of other actors blogs. For this particular online actor, it may be more appropriate to analyze the text that appears in his or her comments (as opposed to just the inlinks) to determine which relationships are most important. As an additional example, the frequency of postings may be significant where two actors that are somehow related tend to respond to each other very quickly.

In any case, a graphical representation of an online information flow network over a plurality of time periods that illustrates information flow links from primary data sources to secondary data sources may be presented 322 on a user's display using the extracted and/or constructed unique URLs to allow analysts and other users to observe and understand the significance of relationships between authors, articles, and the like from what is often noisy and complicated open source data.

Turning to FIG. 25, another screenshot 520 of the dashboard 346 may be presented to a user upon manipulation of a “Network” button (not shown) that illustrates one or more information flow networks. Here, an information flow network module 370 of the dashboard 346 (see FIG. 3) may function to retrieve information flow network data (as generated by information flow network extraction engine 174 of WISDOM server 14) for a number or websites/posts/etc. from data store 46 of WISDOM server 14 and present a graphical representation of one or more information flow networks on a user's display as shown in FIG. 25.

In this screenshot 520, a number of data source graphical icons 524 (e.g., nodes, dots, circles) may be shown in the presentation section 416, each of which represents a particular data source (e.g., blog posting, website, etc.) corresponding to one or more scenarios or sub-scenarios. The data source graphical icons 524 may be appropriately connected by information flow link graphical icons 528 (e.g., lines), where an arrow or other feature associated with each information flow link graphical icon 528 illustrates a flow of information from a “primary” data source graphical icon 524 to a “secondary” data source graphical icon 524 (i.e., the secondary data source includes an inlink to the primary data source). Each of the data source graphical icons 524 may be appropriately colored, textured, shaped, etc. to indicate the particular type of data source it represents. For instance, and as indicated by legend 440, blog posting data source graphical icons 524 may be colored pink, news article data source graphical icons 524 may be colored blue, and the like. In another arrangement, the data source graphical icons 524 of relatively older data sources (e.g., as measured by their publication date) may be grayed out (or may be associated with a feature different from newer data sources).

This screenshot 520 may also include a time bar 532 that indicates a particular time increment (e.g., day) for which the information flow network shown in the presentation section 416 represents. This view 520 may also include a “play” button 536 that, when manipulated, may cause the presentation section 416 to successively display the particular arrangement of data source and information flow link graphical icons 524, 528 making up the information flow network for each time increment. For instance, upon manipulating the play button 536, the presentation section 416 may display the information flow network for each successive day for a predetermined period of time (e.g., 3 seconds, 10 seconds) before displaying the information flow network for the next successive time increment. The view 520 may also include toggle buttons 538 that allow a user to manually cause the display of a information flow network for a desired time increment.

In one arrangement, moving a user manipulable feature (e.g., cursor, finger) over a data source graphical icon 524 may cause an indication 539 of a URL corresponding to the particular data source graphical icon 524 to be displayed and/or may cause one or more features of the graphical representation of the information flow network to change to its relation to adjacent data source graphical icons 524 to provide a visual indication of data sources interacted with by this particular data source. For instance, moving a cursor or finger over a particular data source graphical icon 524 may cause such data source graphical icon 524 to change to a first color (e.g., green) and any connected data source graphical icons 524 to change to a second color (e.g., orange), where the first and second colors are different from the color(s) of the other data source graphical icons 524. In one arrangement, those data source graphical icons 524 that are “primary” data sources in relation to the selected data source graphical icon 524 may be of a color different than a color of those data source graphical icons that are “secondary” data sources in relation to the selected data source graphical icon 524.

Similarly, the information flow link graphical icons 528 interconnecting the selected primary/secondary data source graphical icons may change to a color (e.g., orange) different from other information flow link graphical icons 528. In one arrangement, those information flow link graphical icons 528 representing information flow towards the selected data source graphical icon 524 may be of one color (e.g., orange) to indicate that the selected data source graphical icon 524 is a “secondary” data source in relation to the data source graphical icons 524 connected to such orange information flow link graphical icons 528, and those information flow link graphical icons 528 representing information flow away from the selected data source graphical icon 524 may be of another color (e.g., yellow) to indicate that the selected data source graphical icon 524 is a “primary” data source in relation to the data source graphical icons 524 connected to such yellow information flow link graphical icons 528.

Turning to FIG. 26, another screenshot 544 is illustrated similar to the screenshot 520 of FIG. 25, but that provides graphical representations of information flow networks at an author level as opposed to the post level as in FIG. 25. For instance, part of the processing performed by the content extraction module 70 of the WISDOM server 14 may be to extract an author from the source code of the webpage or other online data source, and then include the author's name within the generated object 94 stored in data store 46. The information flow network extraction engine 174 of the WISDOM server 14 may then utilize the author names in constructing information flow networks which may be retrieved by the information flow network module 370 of the dashboard 346 for presentation on a user's display.

As shown in FIG. 15, it is envisioned that the toolbox 62 may additionally or alternatively include one or more other analytical tools 182. Furthermore, some of the engines and modules of the toolbox 62 may be able to communicate and/or share information. For instance, the sentiment analysis engine 166 and the signature engine 170 may be able to share word/term frequency metrics for use in their respective analyses.

The dashboard 346 may also additionally or alternatively include a number of other engines or modules 382 operable to obtain particular information from the WISDOM server 14 and/or perform additional analytics on such obtained information. See FIG. 3. Furthermore, the dashboard 346 may include a data export manager 358 operable to coordinate with the WISDOM server 14 and/or other components/processes of the system 10 to export any desired data and/or analytics to any appropriate storage location (e.g., storage module 334 of client device 22) and/or analytical modules or processes.

Turning now to FIG. 28, another screenshot 560 of the dashboard 346 may be presented to a user upon manipulation of a “Data Export” button 410. Here, the data export manager 358 of the dashboard 346 may coordinate with data access layer 54 of WISDOM server 14 to cause the export of any objects 94, the original source code of such objects 94, analytical information, and/or any additional related information to one or more external applications (e.g., Excel) or into one or more file formats (e.g., GraphML) for subsequent use and/or storage by a user (e.g., on storage module 334 of client device 22). For instance, the presentation section 416 of this screenshot 560 may include a number of user manipulable features 564 (e.g., buttons, links) that allow a user to export any desired data (e.g., post URLs, post-post networks, signature words, etc.) to or into a desired application, data format, storage location, and/or the like.

Deviations may be made from the specific embodiments disclosed in the specification without departing from the spirit and scope of the invention. For example, at least some of the functionalities performed by many of the processes and modules discussed herein may be performed by other modules, devices, processes, etc. The illustrations and discussion herein has only been provided to assist the reader in understanding the various aspects of the present disclosure.

Furthermore, the various utilities disclosed herein (e.g., the “content extraction” utility, the “sentiment analysis” utility, the “hierarchical signature determination” utility, and the “information flow network” utility) are not limited to being used in the context of open source information collected via the WISDOM server 14. As previously discussed, numerous other contexts for use and/or implementation of such utilities are envisioned (e.g., data obtained via internal networks, other large volumes of searchable data, and the like).

As also discussed previously, the various engines, managers, modules, and the like disclosed herein may be in the form of any appropriate combination of hardware, software, middleware, firmware and/or the like operable to carry out the various functionalities disclosed herein. For instance, such software, middleware and/or firmware may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by one or more processors or processing modules, or to control the operation of, one or more data processing apparatuses. For example, the engines and tools in the toolbox 62 of backend processing engine 50 of the WISDOM server 14 may be provided in such computer-readable medium and executed by a processor or the like. The computer-readable medium can be a machine-readable storage device (e.g., memory module 26 of WISDOM server 14), a machine-readable storage substrate, a memory device, a composition of matter affecting a machine-readable propagated signal, or a combination of one or more of them. In addition to hardware, the system 10 may include code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.

A computer program (also known as a program, software, software application, script, or code) used to provide the functionality described herein (such as to provide the various online, open source information collection and analysis functionalities disclosed herein) may be written in any form of programming language, including compiled or interpreted languages, and may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by an information flow network.

The block diagrams, processes, protocols and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Generally, the elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. The techniques described herein may be implemented by a computer system configured to provide the functionality described.

In some embodiments, the system 10 (i.e., the WISDOM server 14, client devices 22, etc.) may include one or more of various types of devices, including, but not limited to a personal computer system, desktop computer, laptop, notebook, netbook computer, mainframe computer system, handheld computer, workstation, network computer, application server, storage device, a consumer electronics device such as a camera, camcorder, set top box, mobile device, video game console, handheld video game device, a peripheral device such as a switch, modem, router, or, in general, any type of computing or electronic device.

Typically, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, a digital camera, to name just a few. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry. To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a computer (e.g., client device 22) having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.

While this disclosure contains many specifics, these should not be construed as limitations on the scope of the disclosure or of what may be claimed, but rather as descriptions of features specific to particular embodiments of the disclosure. Certain features that are described in this specification in the context of separate embodiments and/or arrangements can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Additionally, the foregoing description of the present invention has been presented for purposes of illustration and description. Furthermore, the description is not intended to limit the invention to the form disclosed herein. Consequently, variations and modifications commensurate with the above teachings, and skill and knowledge of the relevant art, are within the scope of the present invention. The embodiments described hereinabove are further intended to explain best modes known of practicing the invention and to enable others skilled in the art to utilize the invention in such, or other embodiments and with various modifications required by the particular application(s) or use(s) of the present invention. It is intended that the appended claims be construed to include alternative embodiments to the extent permitted by the prior art. 

1-60. (canceled)
 61. A system for use in creating a hierarchical signature for a website, the system comprising: a processing module; and a memory module logically connected to the processing module and comprising a set of computer readable instructions executable by the processing module to: identify at least one textual hierarchy including at least first and second levels, wherein the first level comprises at least one textual category and the second level comprises at least one term that describes the at least one textual category; determine a number of occurrences of the at least one term from a number of pages of at least one website during a time period; first obtain, using a processing engine, a hierarchical signature of the at least one term that represents a prevalence of the at least one term on the at least one website; second obtain, from the first obtaining step, a hierarchical signature of the at least one textual category that represents a prevalence of the at least one textual category on the at least one website; establish a hierarchical signature of the at least one website utilizing the hierarchical signature of one or more of the at least one term and the at least one textual category; and present, on a display, a graphical representation of the hierarchical signature of the at least one website, wherein the graphical representation illustrates the prevalence of one or more of the at least one term and the at least one textual category.
 62. The system of claim 61, wherein the computer readable instructions that first obtain the hierarchical signature of the at least one term include instructions executable by the processor to: divide the number of occurrences of the at least one term by the number of pages to obtain the hierarchical signature for the at least one term.
 63. The system of claim 62, wherein the at least one term comprises first and second terms.
 64. The system of claim 63, wherein the computer readable instructions that second obtain the hierarchical signature of the at least one textual category include instructions executable by the processor to: average the hierarchical signatures of the first and second terms to obtain the hierarchical signature for the at least one textual category.
 65. The system of claim 63, wherein the computer readable instructions further include instructions executable by the processor to: normalize the signatures of the first and second terms.
 66. The system of claim 65, wherein the computer readable instructions that normalize the signatures of the first and second terms include instructions executable by the processor to: ascertain a mean and standard deviation of the first and second term hierarchical signatures; subtract the mean from each of the first and second term hierarchical signatures; and divide each of the values from the subtracting by the standard deviation to obtain z-scores for each of the first and second term hierarchical signatures, wherein the graphical representations of the first and second term hierarchical signatures respectively correspond to the z-scores of the first and second term hierarchical signatures.
 67. The system of claim 61, wherein the at least one textual category comprises a plurality of textual categories, and wherein the website hierarchical signature comprises the hierarchical signatures of each of the plurality of textual categories.
 68. The system of claim 67, wherein the computer readable instructions that establish the hierarchical signature of the website include instructions executable by the processor to establish hierarchical signatures for a plurality of websites, and wherein the computer readable instructions further include instructions executable by the processor to: discover at least one website community from the plurality of web sites; and utilize the hierarchical signatures of the websites making up the website community to obtain a hierarchical signature for the website community.
 69. The system of claim 68, wherein the computer readable instructions that utilize the hierarchical signatures of the websites include instructions executable by the processor to: average the hierarchical signatures of the websites making up the website community to obtain the hierarchical signature for the website community.
 70. The system of claim 61, wherein a first color of the graphical representation represents a first prevalence of the at least one term and/or at least one textual category on the at least one website and a second color of the graphical representation represents a second prevalence of the at least one term and/or at least one textual category on the at least one website, and wherein the first prevalence is higher than the second prevalence.
 71. The system of claim 61, wherein the computer readable instructions further include instructions executable by the processor to: receive, at the processing engine, parameters used to perform a query for the at least one website from a plurality of websites; and utilize the query parameters to identify the at least one textual hierarchy.
 72. (canceled)
 73. The system of claim 61, wherein each of the pages of the at least one website comprises an object that includes content of interest that has been extracted from the at least one website by way of computer readable instructions executable by the processor to: obtain source code used to generate the page on a display, wherein the source code includes a plurality of elements and each element includes at least one tag comprising at least one tag type; parse the source code to obtain a node tree including a plurality of nodes arranged in a hierarchical structure, wherein each node comprises one of the elements, and wherein one of the plurality of nodes comprises a root node; determine a tag type of a node under the root node; assign a heuristic score to the node based at least in part on the tag type of the node; continue to determine and assign for one or more additional nodes of the node tree; and generate, the object, wherein the content of interest is associated with nodes of the node tree having heuristic scores indicating that such content is of interest. 74-82. (canceled)
 83. A system for use in inferring an online information flow network, the system comprising: a processing module; and a memory module logically connected to the processing module and comprising a set of computer readable instructions executable by the processing module to: receive information related to a plurality of portions of source code used to generate a plurality of online data sources, wherein the information allows a uniform resource locator (URL) to be obtained for at least one of the data sources; determine, from the information using a processor, whether any of the plurality of online data sources refers to another online data source during a first of a plurality of time periods, wherein any online data source that refers to another online data source comprises a “secondary data source”, and wherein any online data source that is referred to by another online data source comprises a “primary data source”; in response to at least some of the plurality of online data sources referring to other online data sources, obtain, from the information, a unique URL for each of the primary and secondary data sources; continue to determine and obtain for additional time periods; and present, on a display, a graphical representation of an online information flow network that illustrates one or more information flow links connecting and representing information flows from primary data sources to secondary data sources over the plurality of time periods.
 84. The system of claim 83, wherein at least one of the primary and secondary data sources comprises a posting on a website, and wherein the computer readable instructions that obtain the unique URL for each of the primary and secondary data sources include instructions executable by the processor to: construct the unique URL of the posting by utilizing a URL of the website and a identifier of the posting.
 85. (canceled)
 86. The system of claim 83, wherein in the graphical representation of the online information flow network, each of the data sources and information flow links comprises a respective graphical icon, and wherein in response to a user manipulable device being positioned over a primary data source graphical icon, the computer readable instructions further include instructions executable by the processor to: modify a feature of the primary data source graphical icon; modify a feature of any secondary data source graphical icons of the primary data source graphical icon; and modify a feature of the information flow link graphical icons connecting the primary data source graphical icons and the secondary data source graphical icons.
 87. The system of claim 86, wherein after the processor has executed the computer readable instructions to modify the features of the primary data source graphical icon, secondary data source graphical icons, and information flow link graphical icons, the primary data source graphical icon comprises a first color, the secondary data source graphical icon(s) comprises(s) a second color, and any other data source graphical icon(s) comprise(s) a third color, wherein the first, second and third colors are different.
 88. The system of claim 86, wherein after the processor has executed the computer readable instructions to modify the feature of the information flow link graphical icons, the information flow link graphical icons representing information flow from the primary data source graphical icon to the secondary data source graphical icons comprise a first color that is different from the other information flow link graphical icons of the graphical representation of the online information flow network.
 89. The system of claim 88, wherein the information flow link graphical icons representing information flow from other data source graphical icons to the primary data source graphical icon comprise a second color different from the first color, and the other information flow link graphical icons comprise a third color different from the first and the second colors.
 90. The system of claim 86, wherein in response to the user manipulable device being positioned over the primary data source graphical icon, the computer readable instructions include further instructions executable by the processor to: present, on the display, a graphical representation of the unique URL of the primary data source.
 91. The system of claim 83, wherein the computer readable instructions include further instructions executable by the processor before the processor has executed the computer readable instructions to receive information related to a plurality of portions of source code used to generate a plurality of online data sources to: obtain the portions of source code, wherein the each portion includes a plurality of elements and each element includes at least one tag comprising at least one tag type; parse the portions of source code to obtain a node tree including a plurality of nodes arranged in a hierarchical structure, wherein each node comprises one of the elements, and wherein one of the plurality of nodes comprises a root node; determine a tag type of a node under the root node; assign a heuristic score to the node based at least in part on the tag type of the node; continue to determine and assign for one or more additional nodes of the node tree; and generate an object for each of the portions of source code that includes content associated with nodes of the node tree having heuristic scores indicating that such content is of interest, wherein the information comprises the objects. 